Internet Info 1997 December/Internet_Info_CD-ROM_Walnut_Creek_December_1997.iso/ietf/urn/urn-archives/urn-ietf.archive.9612/000010_owner-urn-ietf _Mon Dec 16 15:43:45 1996.msg

Internet Message Format | 1997-02-19 | 2KB

Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id PAA16508 for urn-ietf-out; Mon, 16 Dec 1996 15:43:45 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id PAA16497 for <[e-mail]>; Mon, 16 Dec 1996 15:43:41 -0500
From: [e-mail]
Received: from windrose.omaha.ne.us by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b)
        id AA12260  (mail destined for [e-mail]); Mon, 16 Dec 96 15:43:35 -0500
Message-Id: <[e-mail]>
Date: Mon, 16 Dec 96 14:42 CST
To: [e-mail], [e-mail]
Subject: Re: [URN] Pre-release of draft-ietf-urn-syntax-02.txt
X-Sun-Charset: US-ASCII
Sender: [e-mail]
Precedence: bulk
Reply-To: [e-mail]
Errors-To: [e-mail]

> >5. The NSS is case sensitive, while the NID, "urn:" tag and %escaping
> >are case insensitive.
>     Why is the NSS case sensitive?  Most people are used to URL's which
> are case insensitive.  There would be a lot of confusion with people
> ignoring caps, as well as allowing someone to take an NSS which is
> identicle to another except for capitalization.  (I think there was a
> similar issue recently with URL's and the three letter classification.)

I disagree that all URLs are case insensitive.  Portions are, but then again,
some portions aren't.

Going back into my email archives (not as thorough as Bunyip's, but easier
to get at, the syntax draft has always allowed individual namespaces to
declare themselves as having a case-insensitive NSS, but that is not the
default.  Further, there was some discussion that case-insensitivity would
have strange effects in the international arena (Martin, maybe you
can clarify this some more?)

Ryan